GLExcess/XSMark v1.2
  

Author:
Paolo "Bustard" Martella 
Last Updated:
07/21/2002 

Upload and compare your results at XSMark official site

Table of contents
                      What's new in version 1.2
                        Command line arguments
                                     XSscript utility
                    Frequently Asked Questions
               Contacts and acknowledgments
  What's new in version 1.2


New in version 1.2:

  • Hashed HTML report
  • Bug fixes

New in version 1.1a:

  • Automatic VSYNC management
  • Command line arguments added
  • XSscript scripting utility added
  • Bug fixes

New in version 1.1:

  • Auto detection of suitable video resolutions
  • Demo and benchmark modes all in one single program
  • More accurate benchmarking
  • Benchmark mode generates detailed reports in HTML format
  • User configurable benchmark tests
  • Benchmark tests run faster for quick performance reports
  • Generated reports can be uploaded and compared to other users's

New in version 1.0b:

  • Added FPS counter and performance reports

Version 1.0:

  • Demo mode only
  Command line arguments


Version 1.2
can be run with command line arguments. Here is a complete list of the arguments allowed for glxsv1.2.exe file:

  • [b/d] - switches between benchmark and demo modes
  • r wxh@b - runs the application at the desired resolution and color depth (w stands for width, h for height and bpp for color depth)
  • f [0/1] - switches between fullscreen (1) and windowed (0) modes
  • g xxx - sets desired brightness (xxx can be any integer value from 0 to 255 - setting the brightness at 128 will not change your monitor brightness)
  • m [0/1] - DEMO MODE ONLY - enables (1) or disables (0) music
  • f [0/1] - DEMO MODE ONLY - enables (1) or disables (0) sound effects
  • l [0/1] - DEMO MODE ONLY - enables (1) or disables (0) demo looping
  • s x,y,...,z - BENCHMARK MODE ONLY - sets which scenes will be run - multiple scenes must be seperated with the 'comma' (,) character and can be any integer value between 1 and 12
  • d [0/1] - BENCHMARK MODE ONLY - if set to 1, this parameter tells GL Excess to display test results at the end of the benchmark
  • n string - BENCHMARK MODE ONLY - sets the name of the benchmark that will be shown on results page

WARNINGS

  • You must specify ALL the parameters above in order to run the application
  • Windowed mode will force the application to run at desktop color depth; this option may result in unaccurate performance testing and thus is not recommended

EXAMPLES OF USAGE

BENCHMARK MODE
glxsv1.2.exe -b -r 640x480@16 -f 1 -g 64 -s 1,2,3,4 -d 0 -n Std

DEMO MODE
glxsv1.2.exe -d -r 640x480@16 -f 1 -g 64 -m 1 -f 1 -l 1

MORE OPTIONS

VSYNC TEST
glxsv1.2.exe -v

CLEAR RESULTS PAGE
glxsv1.2.exe -c

ENUMERATE DISPLAY DEVICES
glxsv1.2.exe -y

NOTICE

If no command line is specified, the application will run with the parameters saved in GLExcess configuration file (glxs11.cfg - generated by XSconfig.exe program).

  XSscript utility


In order to generate command line options easier, I've written a simple application called XSscript which is included in GL Excess version 1.2.
XSscript will let you run multiple benchmarks automatically and with very little configuration effort. Here is a simple description of the main features:

  1. Insert the name of the batch file that will be generated here (.bat extension)
  2. Switch between fullscreen and windowed mode; this setting will affect all multiple benchmarks
  3. This option lets you choose whether multiple benchmarks will be run automatically or user input is requested before each benchmark starts
  4. When enabled, this option will display the results page each time one of multiple benchmark has been completed; intended for user-input driven multiple benchmarks
  5. Insert a name for your project here
  6. This section of the panel lets you choose which scenes will be run; these setting will affect all multiple benchmarks
  7. This listbox accepts multiple selections (use CTRL and SHIFT keys); in this way you can choose to run multiple benchmarks, one for each resolution which has been selected
  8. When clicked, this button will save to disk the script generated with the options selected
  9. When clicked, this button will save to disk and immediately run the script generated with the options selected
  Frequently Asked Questions

 How do I disable VSYNC on my system?

 How can I activate sound options in GL Excess 1.1+ configuration panel?
 I don't have no sound card installed. Will GL Excess run on my  machine?
 On some scenes FPS count is affected by particular video effects. So how can
 performance reports be accurate?
 Why won't GL Excess run fine on my Matrox video card?
 Benchmark mode 'hangs' right before results page is shown. How can this be?
 Will GL Excess run on my particular Microsoft OS? What if I have a dual CPU
 system?
 I just can't figure out how summaries are calculated. Could you please explain
 this to me?
 How did you generate that particular video effect?
 How long did you take to develop GL Excess? Which tools did you use in the
 making of GL Excess?
 I get xxxx XSMarks on my particular system. Is this result any good?
 How do I upload my results?

 How do I disable VSYNC on my system?

On some video cards (mainly nVidia) GL Excess v1.2 will do the work for you when running a benchmark in fullscreen mode; otherwise you will have to disable this feature manually from your vendor's driver control panel. For those who don't know, disabling vertical synchronization to your monitor refresh rate greatly improves preformance; the price to pay is slightly worse image quality.

 How can I activate sound options in GL Excess 1.1+ configuration panel?

In order to activate sound options a previous version of GL Excess with sound included is required:

  • glxshsnd.exe        (High Quality Sounds - 18 MB)
  • glxslsnd.exe         (Low Quality Sounds - 10 MB)

Download one of these files from Files page and then simply copy "data.pk1" file from one of the archives above into GL Excess 1.1+ folder. Audio options will be automatically activated. Please notice that audio options and looping are only available in demo mode.


 I don't have no sound card installed. Will GL Excess run on my  machine?

Sorry, it won't. GL Excess uses FMOD sound system to perform all timing operations.

 On some scenes FPS count is affected by particular video effects. So how can  performance reports be accurate?

As you run benchmark tests you can see that the FPS bar goes brighter and darker. This means that GL Excess is only recording your FPS performance when the bar is lit, thus testing your system only when it's stressed.

 Why won't GL Excess run fine on my Matrox video card?

This is mainly a driver issue so make sure you have the latest version installed, but I'll let James Crowson (GL Excess user) answer this for you:

Matrox has come out with the 5.71 beta drivers for win2k. These drivers fix many of the bugs that have plagued GlExcess on Matrox cards in the past, however, the most annoying bug is way worse. Also they appear to be quite a bit slower. In the Facescape scene, polygons no longer disappear except at very close range (near the bottom of the screen). In older drivers polygons would randomly disappear from all over. In Crypt, the bump-mapped circle at the end is no longer overbright. In Shiny Waters, the shininess no longer disappears in square patches in the distance - it now looks like the screenshots on your site. Also, the bilinear filtering bug has been fixed. The bug that has gotten worse is flickering polygons. In most scenes some polygon or another flickers on and off quickly. These are beta drivers, so maybe the remaining problems will be fixed soon.

Thanks James!


 Benchmark mode 'hangs' right before results page is shown. How can this  be?

This bug has been reported by a very small number of users. I'm currently looking into the problem, but it seems like this is due to overclock. Also, please remember to switch off any manager program (such as MS Office shortcut task bar, for example) before you run any test. Thanks to Stephan Gⁿnther for this info bit.

 Will GL Excess run on my particular Microsoft OS? What if I have a dual CPU  system?

GL Excess v1.2 has been proved to run fine on Windows 9x, ME, NT, 2000 and XP platforms, in combination with nVidia video cards. Should you have more than one CPU installed on your machine, GL Excess will only detect and use CPU0.

 I just can't figure out how summaries are calculated. Could you please  explain  this to me?

Summaries refer to scenes marked with the same color and NOT to three scenes above. This is the reason why you can get a full XSMark and all summaries just by running the first four scenes. In the example below, summary #4 (big arrow) refers to scenes #2, #7 and #8 (small arrows) and NOT to scenes #10, #11 and #12.



 How did you generate that particular video effect?

For a brief description of the code behind each scene please visit Screenshots page. For more in-depth coverage I'm afraid you will have to wait until GL Excess goes open source (it won't be long though...).

 How long did you take to develop GL Excess? Which tools did you use in the  making of GL Excess?

Get the answer at About me page and About GLXS page.

 I get xxxx XSMarks on my particular system. Is this result any good?

Please refer to XSMark HomePage or visit XSMark Section of GL Excess official FORUM.

 How do I upload my results?

Please refer to XSMark HomePage to get all the information you need.
  Contacts and acknowledgments


If your question is not listed in the FAQ's, please feel free to contact me at the following email address: bustard@glexcess.com

I wish to thank my friends (random order) Giovanni Scarrone and Marco Remondino at Hardware Zone, Jeff Molofee, Kris Toole (thanks for the wonderful T-shirt pal!), Julian Spillane, Lorenzo Seguiti, Marco Ruzzi, Simone Nobili and Giovanni dal Negro for their support and dedication.

Special thanks to all v1.1a beta-testers (random order): Florian Mⁿssig at Krawall, Henry Hesse, Nadine Landau, Timo Kliemchen, Stephan Gⁿnther, Pascal Binggeli, Chad Olson, Bernie Cavanagh, Anthony Walsh, Raffaele Fanizzi.